test(website): cover live production approval flows - #1098
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
blove
enabled auto-merge (squash)
September 14, 2026 03:18
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Production page and endpoint checks could pass while an invalid provider key caused an HTTP-200 agent stream to close without a reply. Add five live canaries to the existing post-deployment smoke suite: refund approval/cancellation, Mastra reservation approval/cancellation, and an AG-UI demo reply.
Each requires RUN_FINISHED and rejects RUN_ERROR. Approval cases verify the dialog payload, submitted decision, dialog closure, and matching result; Mastra also correlates the resumed tool result. These checks use deployed credentials and do not skip when the runner lacks a local provider key. Sequential execution, one retry, and 120-second test timeouts bound provider usage.
Validation:
No public API or documentation behavior changes.